- 
                Notifications
    You must be signed in to change notification settings 
- Fork 87
Naga add hardcoded keysets #866
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| This is blocked until  | 
…hs` higher api function
…rotocol/js-sdk into naga_add_hardcoded_keysets
| Linking this PR: https://github.com/LIT-Protocol/lit-assets/pull/2164 | 
…test-published-sdk feat(e2e): add script to test published packages with e2e tests
| This PR has been tested locally but not against a live network | 
| 
 We will be using this branch to release a  Or, we could add an optional network-specific overrides to handle this kindda thing, but that's another topic. | 
| My apologies @GTC6244 @DashKash54 This PR was accidentally merged as the same time when I merged this pr #877 (to fix the types) to the naga main branch. I will create a new branch and re-add the changes for this branch, will update here. --- Updated here | 
Description
Updates to the latest
developbuild ofnetworkContext.jsonto catch keysets. Adds a hardcodednaga-keyset1value, since this is the coding inlit-noderight now.Adds a LICENCE file for the
wasmpackage ( suppresses a warning! )Removes
wasm-optfor the release build of thewasmpackage. Might be a local descrepency.Type of change
How Has This Been Tested?
e2e tests are passing